docs(install): point self-hosters at the self-host image - #618
Merged
Conversation
The upgrade guide and the 1.0 announcement both told self-hosters to pull ghcr.io/testplanit/testplanit:latest. That is the hosted-service image: it bakes BASE_DOMAIN at build time and is published for linux/arm64 only, so on an x86 host the pull fails outright with no matching manifest for linux/amd64 The image self-hosters want is testplanit-selfhost — domain-agnostic and multi-arch, and already what the Helm chart and Kubernetes guide default to. Points the two remaining references at it and explains the split, so the choice is not guesswork. Historical release posts keep their original commands: those were correct when written, before the images diverged.
Contributor
Author
|
🎉 This PR is included in version 1.0.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
therealbrad
added a commit
that referenced
this pull request
Sep 8, 2026
The upgrade guide and the 1.0 announcement both told self-hosters to pull ghcr.io/testplanit/testplanit:latest. That is the hosted-service image: it bakes BASE_DOMAIN at build time and is published for linux/arm64 only, so on an x86 host the pull fails outright with no matching manifest for linux/amd64 The image self-hosters want is testplanit-selfhost — domain-agnostic and multi-arch, and already what the Helm chart and Kubernetes guide default to. Points the two remaining references at it and explains the split, so the choice is not guesswork. Historical release posts keep their original commands: those were correct when written, before the images diverged. (cherry picked from commit ec28e83)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The upgrade guide and the 1.0 announcement both told self-hosters to pull
ghcr.io/testplanit/testplanit:latest. That is the hosted-service image — it bakesBASE_DOMAINat build time and is published forlinux/arm64only, so on an x86 host the pull fails outright:The image self-hosters want is
testplanit-selfhost: domain-agnostic and multi-arch (linux/amd64+linux/arm64). It is already what the Helm chart and the Kubernetes guide default to; only these two references were left pointing at the wrong one.Changes:
docs/docs/installation.md— the routine Docker upgrade and the pre-1.0 baselinedocker run, plus a short note explaining which image is whichdocs/blog/2026-09-08-v1.0-release.md— the 1.0 upgrade commandHistorical release posts are left alone: their commands were correct when written, before the two images diverged.
Type of Change
How Has This Been Tested?
pnpm --filter docs buildcompiles clean, and no references to the SaaS image remain anywhere underdocs/docs/or in the 1.0 post.Verified against the registry that the self-host tags now resolve multi-arch:
Checklist
Additional Notes
This was live-breaking for x86 self-hosters following the 1.0 upgrade instructions, since
testplanit-selfhostdid not exist at all until tonight.